<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
    pageEncoding="ISO-8859-1"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>If and only if the service/library/thing provided by the client don't do correctly the job - OR - we're on a regular project</title>
</head>
<body>
	<a href="index.jsp">Back</a> 
	<hr/>
	<p>The business layer is intended to have logics that aren't solved by 
	getting data from a single source. For example, we need to do 3 queries to
	our databases to assemble some data to retur to the client. This isn't 
	enough motivation to create a business layer. But if we need to acces 
	CICS/CTG, an EJB, an SOAP service and do some queries aswell we'll need to
	create a business component to organize such heterogeneous flow.</p>
	<p>Inside "WIS - Next Generation" context, we only will create a java class
	to fullfill the business role if needed. Usually the client have some 
	webservice or '.dll' or '.so' that we just consume. We're not going to 
	create dumb business components that does nothing but bypass data. We access 
	the persistence layer directly from controller instead. Since we're doing as 
	less code as possible, by not having dumb classes we shrink the ammount of
	produced artifacts.</p>
	<p>But in the context of regular projects, where we are responsible to do 
	all business inteligence, our business layer could be more representative, 
	but we sill follow the rule about the usefulness. Except for controller 
	layer, no java artifact will be allowed to just bypass data.</p>
	<p>The principal (not to say the only) language used in this layer is the 
	Java Language.</p>
</body>
</html>